Tom,
Using the Screen Editor I assigned a hotkey to the Rew and For button (F4 and F6) in KMotionCNC but the keyboard buttons are not working. Is there something else i need to do?

Also, is there a Horizontal bar Slider for Feed and Spindle override?

Thanks,
Troy

Hi Troy,

Here is a patch that should allow hotkeys to work with Momentary Buttons such as the Forward and Reverse buttons that wasn't previously supported.
http://dynomotion.com/Software/Patch/ForwRevMomentaryHotKeys_V4.34j/KMotionCNC.exe

Note the Forward and Reverse Buttons should be configured with Momentary Styles (that should be the default and forced).

No sorry the Sliders are fixed as Vertical Sliders.

Regards
TK

 

Tom,
Using the Screen Editor I assigned a hotkey to the Rew and For button (F4 and F6) in KMotionCNC but the keyboard buttons are not working. Is there something else i need to do?

Also, is there a Horizontal bar Slider for Feed and Spindle override?

Thanks,
Troy

Hi Tom,
Got patch installed and set Rew,Fwd buttons.And they are now working with keyboard buttons. But, now i have an odd issue.
When overriding spindle speed by using on screen slider, i was able to click on slider and use up and down arrow keys on keyboard. Now i have to hold the Shift key while pressing a arrow key.

Also, when editing a G Code in KMotionCNC ,the arrow keys wont  move the cursor in any direction. Problem is also in the MDI line.

I double checked my keyboard by using Notepad and there is no issue.

Did i set something wrong?

Thanks,
Troy

Hi Troy,

It's impossible to get anything past you :)

Please try it again.

Regards
TK

 

Hi Tom,
Got patch installed and set Rew,Fwd buttons.And they are now working with keyboard buttons. But, now i have an odd issue.
When overriding spindle speed by using on screen slider, i was able to click on slider and use up and down arrow keys on keyboard. Now i have to hold the Shift key while pressing a arrow key.

Also, when editing a G Code in KMotionCNC ,the arrow keys wont  move the cursor in any direction. Problem is also in the MDI line.

I double checked my keyboard by using Notepad and there is no issue.

Did i set something wrong?

Thanks,
Troy

Hi Tom,
I like to try. :) But my part is easy ;)

Cursor issue with arrow keys is fixed.

Now i have another. I set F2 as my rewind button, Keyboard jog as F12 and F4 as Forward button. The F2 will not work as Rewind but other F buttons do. Currently the F12 and F4 work but not F2.
Is F2 only for Keyboard Jog?

Thanks,
Troy

Hi Troy,

I can't reproduce that problem.

Are you sure you don't have F2 configured for another button somewhere?

Maybe you could send us a simple screen set that demonstrates the problem?

Regards
TK

 

Hi Tom,
I like to try. :) But my part is easy ;)

Cursor issue with arrow keys is fixed.

Now i have another. I set F2 as my rewind button, Keyboard jog as F12 and F4 as Forward button. The F2 will not work as Rewind but other F buttons do. Currently the F12 and F4 work but not F2.
Is F2 only for Keyboard Jog?

Thanks,
Troy

Hay Tom,
 I put my current 3 screens in files section. Still cant get the F2 to work as Rewind button.
https://groups.yahoo.com/neo/groups/DynoMotion/files/HurcoMill1/

Troy

Hi Troy,

It seems the HotKeys are not defined correctly or consistently.

On the Auto Screen: The Keyboard Jog Button and Reverse Button have a duplicate Hotkey definition as F2
Also on the Graphics screen Keyboard Jog Button defined as F2 (even though both are hidden) maybe not an issue.

I assume you were thinking because the Keyboard Jog Button is hidden it shouldn't matter.  I suppose we could make it work that way.  But there might be cases where one would like a hot key to work even if the button is hidden.

Maybe there should be a warning or a button to test for hotkeys used in a duplicate manner within a screen?

Regards
TK

 

Hay Tom,
 I put my current 3 screens in files section. Still cant get the F2 to work as Rewind button.
https://groups.yahoo.com/neo/groups/DynoMotion/files/HurcoMill1/

Troy

Hi Tom,
 That didnt even cross my mind. I keep thinking of my screens as being separate controls from one another. (Thats how i would like them to work anyhow.)
Agree with you on a warning of some sort for duplicate hotkeys.

On a similar note, can an option for buttons/controls hidden on a particular screen be turned off also? Reason being i had an instance where i was on my AUTO screen (which is just for running Gcode) and hit the keyboard Enter Key and it executed what was on my MDI line on my MANUAL screen. Fortunately it was just a small X move and Z was home.
I also have some sort of issue when hitting Feed hold right before a G84 starts. The Spindle stops and Z axis stop, then hitting Cycle Start again nothing happens but tap cycle is still active and trys to randomly restart after restarting gcode.(its not very repeatable) . The only way to resume is ESTOP and INIT. Then restart gcode.
Sorry for jumping around on ya there. :} Just started my own shop past 2 weeks and been working around stuff like that. Bit tired. ;)

Thanks,
Troy

Hi Troy,

Good idea.

Here is an updated patched version of KmotionCNC that will disable the Enter Key doing the MDI Send if either the MDI or the Send buttons aren't visible.
http://dynomotion.com/Software/Patch/ForwRevMomentaryHotKeys_V4.34j/KMotionCNC.exe

Also a Version of the KMotionCNC Screen Editor with a button to check for HotKey Duplicates within a screen set:
http://dynomotion.com/Software/Patch/ForwRevMomentaryHotKeys_V4.34j/KMotionCNCScreenEditor.exe

Regarding G84: can you post your latest G84 C Code for us to look at?  I thought we had those race conditions handled.

Regards
TK

 

Hi Tom,
 That didnt even cross my mind. I keep thinking of my screens as being separate controls from one another. (Thats how i would like them to work anyhow.)
Agree with you on a warning of some sort for duplicate hotkeys.

On a similar note, can an option for buttons/controls hidden on a particular screen be turned off also? Reason being i had an instance where i was on my AUTO screen (which is just for running Gcode) and hit the keyboard Enter Key and it executed what was on my MDI line on my MANUAL screen. Fortunately it was just a small X move and Z was home.
I also have some sort of issue when hitting Feed hold right before a G84 starts. The Spindle stops and Z axis stop, then hitting Cycle Start again nothing happens but tap cycle is still active and trys to randomly restart after restarting gcode.(its not very repeatable) . The only way to resume is ESTOP and INIT. Then restart gcode.
Sorry for jumping around on ya there. :} Just started my own shop past 2 weeks and been working around stuff like that. Bit tired. ;)

Thanks,
Troy

Hi Tom,
 The last version 4.34i, there was a patch made for ridged tapping. But, here is my current ridged tap c program.
https://groups.yahoo.com/neo/groups/DynoMotion/files/HurcoMill1/
I cant remember just what we did to handle feedhold.

Troy

Hi Troy,

Thanks for the file.  I'm a bit confused.  Is the problem with FeedHold just before the Tap or Halt just before the Tap?  You said Feedhold but then you said you hit Cycle Start to attempt to continue.

Also if you might do me a favor and check a few things.  When you have the problem please check if the Tap Program is still running by checking KMotion.exe C Programs Screen to see if there is a green bar on the Thread configured to be used by the Tap Program.

Also check the state of the Feedhold Tap Flag which is persist variable 50.  On the Console Screen enter:

GetPersistDec 50

Thanks
TK

 

Hi Tom,
 The last version 4.34i, there was a patch made for ridged tapping. But, here is my current ridged tap c program.
https://groups.yahoo.com/neo/groups/DynoMotion/files/HurcoMill1/
I cant remember just what we did to handle feedhold.

Troy

Tom,
There appears to be a couple issues with tap.
 My first one is when hitting feed hold between when G43 is turned on for tap and during the Z clearance move.

Second issue is when i Feedhold during Tap cycle, spindle and Z stop.The console says Pitch .03125, command GetPersistDec50 reports a -2. After this i click Stop and GetPersistDec50 reports a -2 and still Pitch .03125. Then i click my Z Home user button which executes gcode G53 G0 Z0. Z rapids home as it should then rapids back down to where Tap cycle was stopped and finishes tap cycle for that hole. After this the console reads a lot of Tap Sync Failed then one Tap Cycle Complete at end. Another command GetPersistDec50 reports -2.

Hope that made sense. :)

Thanks,
Troy

Hi Troy,

Sorry a couple more questions :)

Issue #1: I don't understand.  Did you mean to say G84?  Do you mean after the Tap is finished and while Z is moving up Feedhold is issued and causes a problem?  What happens?

Issue #2: Clicking "Stop" should disable all axes and also kill all C Programs (except Thread #1).  What Thread is the Tap M119 configured to execute in?  Also how can you home without re-initializing and enabling the Axes?  Please post your Home program.

Regards
TK

 

Tom,
There appears to be a couple issues with tap.
 My first one is when hitting feed hold between when G43 is turned on for tap and during the Z clearance move.

Second issue is when i Feedhold during Tap cycle, spindle and Z stop.The console says Pitch .03125, command GetPersistDec50 reports a -2. After this i click Stop and GetPersistDec50 reports a -2 and still Pitch .03125. Then i click my Z Home user button which executes gcode G53 G0 Z0. Z rapids home as it should then rapids back down to where Tap cycle was stopped and finishes tap cycle for that hole. After this the console reads a lot of Tap Sync Failed then one Tap Cycle Complete at end. Another command GetPersistDec50 reports -2.

Hope that made sense. :)

Thanks,
Troy

Hi Tom,
 Text can be hard to convey sometimes. ;)

1) I purposed to say G43. Right after this line of gcode G43 H2( turns on tool length offset) and before G84 tap cycle is where i hit Cycle Pause. What happens sometimes, is spindle shuts off and axis pauses as it should. Then releasing feedhold nothing happens. Spindle should turn back on and Z should continue to clearance plane, G84 cycle is started,Z moves to Reference plane, then synced tapping starts.

 The only way to continue safely, after Feed Hold, is to ESTOP and restart gcode at tapping tool and dont Cycle Pause or Halt.

2)When i say stop i mean Halt not ESTOP.Sorry. :}
M119 is in thread 2/ VAR 50.
My Z home button does not reference. It simply sends axis to home position using G53 G0 Z0. Which sends machine back to Machine Zero, where it was referenced.
Here is my Reference Program and Home (G53 G0) program.
https://groups.yahoo.com/neo/groups/DynoMotion/files/HurcoMill1/

Thanks,
Troy

Hi Troy,

See how this now behaves:

#1 - patch GCodeInterpreter to wait until all motion before Rigid Tap finishes before switching FeedHold mode from Normal to special RigidTap mode.

http://dynomotion.com/Software/Patch/FixFeedholdJustbeforeRigidTap_V434j/GCodeInterpreter.dll

#2 - RigidTap C Program now monitors if the Interpreter was halted (JOB_ACTIVE false), and if detected delays until at least 1 second has elapsed since the spindle was stopped and exits.  The delay is intended to avoid Halt immediately de-slaving the Z axis before the Spindle has stopped and breaking the Tap.  Should 1 second be enough?   Note this isn't an issue if you Feedhold first, then wait for the Spindle to Stop, then Halt.  In this case there won't be a delay (assuming the time between Feedhold and Halt is > 1 sec.

http://dynomotion.com/Software/Patch/FixFeedholdJustbeforeRigidTap_V434j/RigidTapCycle+M119%20Feedhold%20Rev%205.c

I cleaned up a bit also hopefully nothing got broken.

Regards
TK

 

Hi Tom,
 Text can be hard to convey sometimes. ;)

1) I purposed to say G43. Right after this line of gcode G43 H2( turns on tool length offset) and before G84 tap cycle is where i hit Cycle Pause. What happens sometimes, is spindle shuts off and axis pauses as it should. Then releasing feedhold nothing happens. Spindle should turn back on and Z should continue to clearance plane, G84 cycle is started,Z moves to Reference plane, then synced tapping starts.

 The only way to continue safely, after Feed Hold, is to ESTOP and restart gcode at tapping tool and dont Cycle Pause or Halt.

2)When i say stop i mean Halt not ESTOP.Sorry. :}
M119 is in thread 2/ VAR 50.
My Z home button does not reference. It simply sends axis to home position using G53 G0 Z0. Which sends machine back to Machine Zero, where it was referenced.
Here is my Reference Program and Home (G53 G0) program.
https://groups.yahoo.com/neo/groups/DynoMotion/files/HurcoMill1/

Thanks,
Troy

Hi Tom,
 Awesome work again. :) This is MUCH better,  But there is 2 more. :)

1)When pause is executed during tap cycle axis and spindle stop nicely and are staying synced. But no movement nor spindle restart happens when pressing pause again nor are the Rew and For buttons available. If i start spindle manually by keyboard shortcut or on screen button, tapping cycle continues until cycle is finished. And if spindle is manually rotated (with a piece of wood. :) ) Z and spindle are still synced, if i continue to rotate spindle in either CW or CCW direction and reach beginning or ending of hole, the spindle will turn on again and finish tap cycle for that hole. In a way this is nice but obviously not safe unless spindle would remain off and wait for user to turn on spindle or prompt user to turn on spindle again to continue. And continuing would end cycle for that hole and continue on to next hole.I for one like the synced option, just wish it would leave spindle off.:) Or maybe be able to use the Rew and For buttons?

 I know we went over this before.Most industry controls dont allow anything besides an ESTOP condition to overdrive a tapping cycle, which i dont like. :)

2) If the Halt button is pressed during tap cycle (when tap is in hole) axis and spindle come to a stop in a synced manner.Testing again by manually rotating spindle, they stay synced and if spindle is  turned back on the tap cycle will continue for that hole until cycle has completed.  Typical standard default would be when a Halt is executed the spindle and axis stops immediately and synced is lost.Which i think is what you would want as a default for most users.

Thanks again,
Troy

If you want it to Halt, stop and then loose sync, how do you plan on getting the tap out of the part? Stopping a tap can get complicated. I think this is probably why industry blocks it. 

Hi murray,
A Halt should be for situation when tool fails or something similar.I dont like the fact that some controllers block it during tap it never made sense to me. The Cycle buttons should never be blocked, this just opens up more room for human error.

The feed hold is what should be used for other controlled scenarios. And it would be really nice if the Rew and For buttons could be used with tapping. :)

Cycle buttons are not grayed for me. Iam using version 4.34j if that makes a difference. They weren't grayed out on last test version.Also using a custom screen.

Troy

Hi Troy,

Found another bug.  Uploading feedhold state of -2 as Hex string "0xFFFFFFFE" instead of decimal string.

Please see what happens with this:
http://dynomotion.com/Software/Patch/FixFeedholdJustbeforeRigidTap_V434j/KMotionCNC.exe

Regards
TK

 

Hi Tom,
 Awesome work again. :) This is MUCH better,  But there is 2 more. :)

1)When pause is executed during tap cycle axis and spindle stop nicely and are staying synced. But no movement nor spindle restart happens when pressing pause again nor are the Rew and For buttons available. If i start spindle manually by keyboard shortcut or on screen button, tapping cycle continues until cycle is finished. And if spindle is manually rotated (with a piece of wood. :) ) Z and spindle are still synced, if i continue to rotate spindle in either CW or CCW direction and reach beginning or ending of hole, the spindle will turn on again and finish tap cycle for that hole. In a way this is nice but obviously not safe unless spindle would remain off and wait for user to turn on spindle or prompt user to turn on spindle again to continue. And continuing would end cycle for that hole and continue on to next hole.I for one like the synced option, just wish it would leave spindle off.:) Or maybe be able to use the Rew and For buttons?

 I know we went over this before.Most industry controls dont allow anything besides an ESTOP condition to overdrive a tapping cycle, which i dont like. :)

2) If the Halt button is pressed during tap cycle (when tap is in hole) axis and spindle come to a stop in a synced manner.Testing again by manually rotating spindle, they stay synced and if spindle is  turned back on the tap cycle will continue for that hole until cycle has completed.  Typical standard default would be when a Halt is executed the spindle and axis stops immediately and synced is lost.Which i think is what you would want as a default for most users.

Thanks again,
Troy

Hi Tom,
Posted earlier but never made it. :(

Tested patch.
When in tap cycle. I hit Pause, spindle and Z come to a controlled stop and are still synced. Releasing pause, spindle and Z continue and finish tap cycle.

When a Halt is executed during tap cycle, Z and spindle come to a controlled stop. Z and spindle stay synced and the only way to clear this is to execute an ESTOP.

Another issue now has to do with enter key and my Reference Axis program.
Whenever a limit switch is triggered i have a pop up stating what axis and what switch has been triggered.
 
When i run my Reference Axis C code program these pop ups happen.Dont need them to during referencing, just couldn't figure out how to shut them off during referencing.
To close pop up user must click OK or hit enter key on keyboard. Now when i hit enter key the reference c code starts all over again, even thow it is already running.

Troy

Hi Tom,
Posted earlier but never made it. :( 3rd try now.

Tested patch.
When in tap cycle. I hit Pause, spindle and Z come to a controlled stop and are still synced. Releasing pause, spindle and Z continue and finish tap cycle.

When a Halt is executed during tap cycle, Z and spindle come to a controlled stop. Z and spindle stay synced and the only way to clear this is to execute an ESTOP.

Another issue now has to do with enter key and my Reference Axis program.
Whenever a limit switch is triggered i have a pop up stating what axis and what switch has been triggered.
 
When i run my Reference Axis C code program these pop ups happen.Dont need them to during referencing, just couldn't figure out how to shut them off during referencing.
To close pop up user must click OK or hit enter key on keyboard. Now when i hit enter key the reference c code starts all over again, even thow it is already running.

Troy

Hi Tom,
Posted earlier but never made it. :( 4th try

Tested patch.
When in tap cycle. I hit Pause, spindle and Z come to a controlled stop and are still synced. Releasing pause, spindle and Z continue and finish tap cycle.

When a Halt is executed during tap cycle, Z and spindle come to a controlled stop. Z and spindle stay synced and the only way to clear this is to execute an ESTOP.

Another issue now has to do with enter key and my Reference Axis program.
Whenever a limit switch is triggered i have a pop up stating what axis and what switch has been triggered.
 
When i run my Reference Axis C code program these pop ups happen.Dont need them to during referencing, just couldn't figure out how to shut them off during referencing.
To close pop up user must click OK or hit enter key on keyboard. Now when i hit enter key the reference c code starts all over again, even thow it is already running.

Troy

Hi Tom,
 Tried patch here is results.

During Tap cycle , executing a cycle Pause , axis and spindle stop in a controlled manner. Releasing Pause Axis and spindle continue tap cycle. This works throughout the tap cycle.

Pressing Stop during tap cycle, axis and spindle stop in a controlled manner. Gcode has stopped running but axis and spindle are still in sync. Must issue an estop to clear sync.

When running my axis reference program there is an issue now.
When axis finds limit switch i have a pop up stating what axis and what switch has been triggered. User then clicks OK or hits Enter on keyboard to close window.
During referencing this window will pop up,(dont need this pop up during referencing but could not figure out how to ignore it.) but next axis will continue to reference. Issue now is, if user hits enter to close pop up, the reference program will start all over again.

Thanks,
Troy